Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove availability zones since AWS ignores them anyway #10

Closed

Conversation

skorfmann
Copy link

This only worked when availability zones were matching all available zones in the region. If provided less or none, there was always a diff and terraform wanted to recreate the cluster.

References

Copy link
Contributor

@max-rocket-internet max-rocket-internet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks!

Copy link
Contributor

@max-rocket-internet max-rocket-internet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, sorry but can you update the README and the examples too?

@antonbabenko
Copy link
Member

Thanks @skorfmann !

This has been fixed in v1.4.0.

@wayneworkman
Copy link

This exact issue is affecting DocumentDB. It totally ignores the availability zones passed into a aws_docdb_cluster and uses all the ones in the region. When I re-run Terraform, it wants to destroy & recreate the cluster with the two availability zones I'm passing in (which don't matter anyways).

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants